Skip to main content
Check and provide your planning data

BETA This is a new service – your feedback will help us to improve it.

Back to dataset table
East Hampshire District Council

Tree

There is a problem

  • 1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1124

reference
684-tree-1
name
1124
tree-preservation-order

undefined

684-tpo-1
uprn
address-text
point
POINT (-1.017460 50.879995)
geometry
MULTIPOLYGON (((-1.017417 50.879991,-1.017419 50.879999,-1.017425 50.880006,-1.017435 50.880012,-1.017446 50.880016,-1.017459 50.880018,-1.017473 50.880017,-1.017485 50.880013,-1.017494 50.880007,-1.017500 50.880000,-1.017503 50.879991,-1.017501 50.879983,-1.017495 50.879975,-1.017486 50.879969,-1.017474 50.879965,-1.017461 50.879964,-1.017447 50.879965,-1.017435 50.879969,-1.017426 50.879975,-1.017420 50.879982,-1.017417 50.879991)))
notes
felled-date
entry-date
2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

  1. Fix the errors indicated
  2. Use the check service to make sure the data meets the standard
  3. Publish the updated data on the endpoint URL